home *** CD-ROM | disk | FTP | other *** search
- Path: inforamp.net!ts28-10
- From: rmorin@inforamp.net (Randy Charles Morin)
- Newsgroups: comp.lang.c++
- Subject: Re: Coding Standards
- Date: Tue, 12 Mar 96 02:46:18 GMT
- Organization: MiddleWorld SoftWare
- Message-ID: <4i2oi9$nfn@sam.inforamp.net>
- References: <4hj8ek$elu@sam.inforamp.net> <4hjh5c$elk@flood.weeg.uiowa.edu> <4hv2tm$e93@news.halcyon.com> <4i1ne4$g99@clarknet.clark.net>
- NNTP-Posting-Host: ts28-10.tor.inforamp.net
- X-Newsreader: News Xpress Version 1.0 Beta #4
-
- In article <4i1ne4$g99@clarknet.clark.net>,
- gusty@clark.net (Harlan Messinger) wrote:
- >Norm Bryar (normanb@halcyon.com) wrote:
- >: Except you can't put consts in a header for everyone to use and you
- >: can't bitwise-OR enum values. #defines still have a place. <===
- >
- >??? What about a header with the line,
- >
- > extern const MyType MYCONST;
- >
- >and a single module with the global definition
- >
- > const MyType MYCONST(/* Initialization parameters here */);
-
- I'll add this to my repertoire. Does this also work with enums.
-
- Say:
- extern enum team {HOME=0,VISITOR};
- and
- enum team {HOME=0,VISITOR};
-
- Don't spend a minute replying though, I can check it myself.
-
- Agrivar
-